Completely anonymous purchasing of goods on a computer network

ABSTRACT

A system for anonymous purchase of goods involving a Carrier who delivers the goods to the CUstomer, comprising the steps of Customer requests a Vendor&#39;s Clickshare-protected URL representing the desire to purchase some physical goods, the Vendor validates the token, determines access rights, and if a purchase is involved, the cost of the content to be delivered, the Vendor checks various Confirmation and Credit Limit thresholds, asking the Customer to confirm the purchase price, if ecessary, the Vendor asks the Customer to select a Carrier from the list of Carriers the Vendors uses, the Vendor asks CVS for a Token that represents the capability to ask a Carrier for a shipping identifier, the Vendor redirects the Customer&#39;s browser to the Carrier&#39;s server, sending the Customer&#39;s Token, the Vendor&#39;s Token, and a basic description of the packages, if available (number, weight, export restrictions), the Carrier Server validates the Vendor&#39;s Token and uses the Customer&#39;s Token to request information about the Customer, primarily their Site-Specific Customer Identifier (SCID), shipping address, and any additional shipping insturcitons stored on the Customer&#39;s Billing Agent (this process is described earlier), if the Carrier Server has not previously seen the SCID, the Server asks the Customer to release from their Billing Agent or otherwise provide the necessary shipping instructions, the Carrier Server assigns a shipping identifier and preliminary shipping costs, if possible, the Carrier Server redirects the Customer&#39;s browser back to the Vendor according to the Vendor&#39;s instrucitons, along with a Digital BoxCar (TM) containing the Server&#39;s response, the Vendor uses the CVS to authenticate the Digital Box Car (TM) and, if appropriate, adjusts the Customer&#39;s retail cost according to theresponse form the Carrier&#39;s Server, the Vendor validates the Customer&#39;s Token and logs the transaction with CVS, along with purchase price, if any, or with an identifier the Carrier will use later to fill in the shipping cost to be paid to the Carrier, the Vendor packages the physical goods, labeling the packages with the shipping identifier received from the Carrier, the Carrier picks up the packages and prints a complete label using the information it received from the Customer of their Billing Agent, if directed by the Vendor&#39;s instructions, the Carrier logs an addendum to the Vendor&#39;s transaction with the wholesale cost of the shiping to be paid directly to the Carrier rather than the Vendor, and the Carrier delivers the goods to the Customer.

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit under 35 U.S.C. 119(e) of U.S. Provisional Application No. 60/242,971 filed Oct. 24, 2000.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

[0002] This invention has been created without the sponsorship or funding of any federally sponsored research or development program.

[0003] Contents

[0004] Overview 4

[0005] Completely Anonymous Purchasing . . . 4

[0006] Definition . . . 4

[0007] Problem . . . 4

[0008] Current Practices . . . 4

[0009] The Clickshare-CAP Solution . . . 6

[0010] Terminology 7

[0011] Customer/User . . . 7

[0012] Vendor . . . 7

[0013] Billing Agent . . . 7

[0014] Carrier . . . 8

[0015] Affiliate . . . 8

[0016] Clickshare-CAP Network . . . 8

[0017] Settlement Agent . . . 8

[0018] Clickshare-CAP Technology 8

[0019] Overview . . . 8

[0020] CAP Validation Service (CVS) . . . 9

[0021] User Authentication Module (UAM) [Billing Agent] . . . 10

[0022] Customer Validation Module (CVM) [Vendor] . . . 11

[0023] Destination Address Resolution Module (DARM) [Carrier] . . . 11

[0024] Site-specific Customer Identifier Module (SCIM) [part of UAM] . . . 12

[0025] Affiliation Certification Module [affiliates] . . . 12

[0026] CAP Settlement Service (CSS) [backend payment distribution] . . . 13

[0027] Information Flow Processes 13

[0028] Starting a Clickshare-CAP Session . . . 13

[0029] Sending Digital BoxCar(TM)s . . . 15

[0030] Basic Anonymous purchase of digital content: . . . 15

[0031] Basic Anonymous purchase involving an Affiliate . . . 16

[0032] Basic Anonymous purchase involving a Carrier (CAP) . . . 17

[0033] Clickshare-CAP Inventions 18

[0034] Completely Anonymous Purchasing . . . 19

[0035] Shipping without an address . . . 21

[0036] Sales without customer account management . . . 22

[0037] Direct payments to Carriers . . . 23

[0038] Customer-Carrier Deals . . . 23

[0039] Anonymous package tracking . . . 24

[0040] Package tracking by Customer without tracking numbers . . . 24

[0041] Real-time information tracking . . . 26

[0042] Customized delivery instructions . . . 27

[0043] Certified Affiliations . . . 27

[0044] Summary 29

[0045] Completely Anonymous Purchasing . . . 29

[0046] CLAIMS . . . 24

[0047] ABSTRACT . . . 25

[0048] Figures . . . 33

[0049] Major Components . . . 33

[0050] Information Flow Processes . . . 2733

BACKGROUND OF THE INVENTION

[0051] Overview

[0052] Completely Anonymous Purchasing

[0053] Definition

[0054] Completely Anonymous Purchasing (CAP) is the ability to purchase physical goods via the Internet or other electronic means without the buyer revealing any personal information to the seller.

[0055] Problem

[0056] Systems currently exist that permit individuals to communicate anonymously with others via the Internet. These systems also permit buyers to purchase digital goods anonymously, since digital goods can be delivered via the same communication channels. When dealing with physical goods, however, the seller must be able to deliver the goods to the buyer through other channels, such as commercial shipping companies, which require personal information such as the name and address of the recipient. Existing systems such as drop boxes and intermediaries provide partial anonymity by allowing a buyer to have the goods shipped to an intermediary who then forwards the goods to the buyer. However, these systems greatly increase the cost of transport in terms of delivery time, expense, the ability to track packages, risk of loss, security, and convenience.

[0057] Thus, the central problem we solve is “providing Completely Anonymous Purchasing using the existing transport infrastructure with no additional costs.”

[0058] Current Practices

[0059] Most physical goods are shipped by commercial carriers such as government run Postal Services, package delivery services such as United Parcel Service and Federal Express, and trucking companies such as Allied Transport, and many others. Regardless of carrier, the remote purchase of physical goods typically involves the following steps:

[0060] 1. Buyer provides Seller with the buyer's name and address.

[0061] 2. Seller enters this information and attaches it to the order information.

[0062] 3. Seller selects carrier (possibly by asking user to select from a small collection of carriers).

[0063] 4. Seller prepares printed shipping instructions in a form appropriate for the selected carrier.

[0064] 5. Carrier takes possession of the goods and brings them to a local collection center.

[0065] 6. Carrier attaches its own labels or codes to the package to help direct the package through the carrier's system.

[0066] 7. Carrier delivers the package to the buyer's address.

[0067] The problem areas are steps 1, 2, and 4. Our solution solves these problems, taking advantage of step 6.

[0068] These and other difficulties experienced with the prior art systems have been obviated in a novel manner by the present invention.

[0069] It is, therefore, an outstanding object of the present invention to provide a system that allows completely anonymous purchasing on a global computer network like the Internet.

[0070] Another object of this invention is to provide a system that allows completely anonymous purchasing of services on a global computer network like the Internet.

[0071] A further object of the present invention is to provide a system that allows completely anonymous purchasing of goods on a global computer network like the Internet.

[0072] It is another object of the invention is to provide which allows completely anonymous purchasing on a global computer network like the Internet while providing customer information to the vendor sufficient to customize the sales transaction for the customer.

[0073] With the foregoing and other objects in view, which will appear as the description proceeds, the invention resides in the combination and arrangement of steps and the details of the process hereinafter described and claimed, it being understood that changes in the precise embodiment of the invention herein disclosed may be made within the scope of what is claimed without departing from the spirit of the invention.

BRIEF SUMMARY OF THE INVENTION

[0074] The Clickshare-CAP Solution

[0075] We solve the Completely Anonymous Purchasing problem by enabling the buyer to provide shipping instructions to the carrier directly. The Seller provides the carrier with the details of the packages to be shipped; the buyer provides the carrier with the shipping address; and the carrier provides the seller with a shipping identifier to place on the packages. When the carrier receives the package from the seller, it converts the shipping identifier to the complete address at the point at which it prints its own labels and delivers the package normally.

[0076] The complete solution utilizes a collection of inventions built upon a unique technology infrastructure that supports anonymous payment and secure, anonymous information exchange. The remainder of this document describes the solution and our inventions in detail. We begin by defining some common terms. We then describe the technology infrastructure and our inventions built using the technology. We end by summarizing how, together, the inventions solve the Completely Anonymous Purchasing problem.

BRIEF DESCRIPTION OF THE DRAWINGS

[0077] The character of the invention, however, may best be understood by reference to one of its structural forms, as illustrated by the accompanying drawings, in which:

[0078]FIG. 1 is a diagrammatic representation of the major components of a system embodying the principals of the present invention,

[0079]FIG. 2 is a diagrammatic representation of a part of the system involving starting a session at a vendor,

[0080]FIG. 3 is a diagrammatic representation of a part of the system involving starting a session at user's agent,

[0081]FIG. 4 is a diagrammatic representation of a part of the system involving sending a Digital BoxCar,

[0082]FIG. 5 is a diagrammatic representation of a part of the system involving anonymous digital purchase,

[0083]FIG. 6 is a diagrammatic representation of a part of the system involving affinity certification, and

[0084]FIG. 7 is a diagrammatic representation of a part of the system involving anonymous physical purchase.

DETAILED DESCRIPTION OF THE INVENTION

[0085] Terminology

[0086]FIG. 1 shows the entities involved in the purchase and delivery of physical goods in our solution. These entities have the following meanings:

[0087] Customer/User

[0088] The Customer or User is the person purchasing the physical goods and requesting delivery to an address of their choosing. This person is the Buyer described in the preceding section. From the Vendor's perspective, this person is their customer. From the perspective of this person's Billing Agent, this person is one of the Agent's Users.

[0089] Vendor

[0090] The Vendor is the organization providing goods to customers. This organization is the Seller described in the preceding section. Although we talk of buying and selling, our solution applies equally well to situations that involve transferring physical goods without payment.

[0091] Billing Agent

[0092] The Billing Agent is the organization chosen by the User to hold and protect the User's personal information and to handle billing the User for their purchases. A Billing Agent may bill Users directly, by making charges on the User's credit card, adding charges to a utility bill, directly debiting a bank account or other pre-funded account, or any other mechanism acceptable to the User. Settlement Agents transfer funds from Billing Agents to Vendors, Carriers, and other entities as specified in transaction logs generated during system operation.

[0093] Carrier

[0094] The Carrier is the organization chosen by the Vendor to deliver the physical goods from the goods' present location to the Customer's location. Typically, a Vendor will use a number of Carriers and may choose to let the Customer select one for a particular shipment.

[0095] Affiliate

[0096] An Affiliate is an organization or other grouping of prospective Customers with whom a Vendor may have a special arrangement. Examples include associations such as AARP and AAA, Customers of other Vendors, subscribers to a particular newspaper or journal, and professional organizations, such as AMA and IEEE.

[0097] Clickshare-CAP Network

[0098] The Clickshare-CAP Network is a collection of web servers and other technology that enables the secure and efficient transfer of the information necessary to support Completely Anonymous Purchasing and associated inventions.

[0099] Settlement Agent

[0100] A Settlement Agent acts as a clearinghouse that ensures that payments and transaction information are properly distributed among the various entities involved in the purchasing and delivery of physical goods. There may be multiple cooperating Settlement Agents run by different organizations.

[0101] Clickshare-CAP Technology

[0102] Overview

[0103] CAP is realized by a collection of inventions built using the Clickshare-CAP Infrastructure Technology. This technology enables the secure and efficient transfer of the information over the Internet, through wireless devices, and over other private networks.

[0104] The system is highly distributed with each player in a transaction responsible for managing the information that relates to that component. There is no central server. The core of the system is the CAP Validation Service (CVS). All of the other modules talk to this service via the Internet to verify the integrity of information passing among the various components.

[0105] The primary unit of information is the Token. A Token represents a capability that can be passed among the components. In its most common use, a Token indicates the presence of a valid Clickshare User Session. When a user authenticates with their Billing Agent, the agent asks the CAP Validation Service to create a new Clickshare User Session. The CVS creates the session and returns a new Token. This Token identifies the session, but contains no information identifying the User. Instead, the Token represents a capability to charge the User's account and, in some cases, to request information about the User. It travels among the components, with each component asking the CVS to verify that the Token is valid and to initiate an operation allowed by the Token. The Token can also be used to represent other capabilities such as the capability for one component to ask information about the User from another component.

[0106] A Digital BoxCar(TM) allows one component to pass information securely to another component. When one component wants to send data to another, it asks CVS to create a hash of the Token and Digital BoxCar(TM) combination. The receiving component can then ask CVS to verify that the Digital BoxCar(TM) is intact when validating the received Token.

[0107] All components in the Clickshare-CAP Network can be replicated to provide Scalability and improved performance and up-time.

[0108] CAP Validation Service (CVS)

[0109] The CAP Validation Service provides runtime validation of information passed among the modules. This component ensures the integrity of the data passing over insecure networks and ensures that the various components are legitimately part of the Clickshare-CAP Network. The primary information it manages are the Tokens that indicate the presence of a valid Clickshare User Session and other capabilities.

[0110] This component can be implemented as a web server that provides a simple interface for other components to use. The basic operations include:

[0111] Create or invalidate a Clickshare User Session

[0112] Validate a Token

[0113] Log a purchase

[0114] Request or validate a capability

[0115] Connect or disconnect a component from the Clickshare-CAP Network

[0116] Transfer a User Session to and from another CVS Server

[0117] User Authentication Module (UAM) [Billing Agent]

[0118] The User Authentication Module allows sites that register users to allow these users to use the Clickshare-CAP Network. Sites employing the UAM are called Billing Agents because they manage all aspects of the User's Clickshare Account, particularly aggregating the charges billed to the User's account and obtaining payment from the User for these charges. This module includes software that provides the following capabilities:

[0119] allows the Billing Agent's user authentication software to communicate with CVS to create new Clickshare Sessions

[0120] allows other components to request user information by presenting a CVS generated Token

[0121] allows the Agent's user account management software to communicate with the Clickshare-CAP Settlement Service, in order to retrieve the transaction logs needed to update their user's accounts.

[0122] This module can be implemented as a collection of web server components (e.g., Java Servlets) and stand-alone programs.

[0123] Customer Validation Module (CVM) [Vendor]

[0124] The Customer Validation Module allows Vendors to connect to the Clickshare-CAP Network and provide Completely Anonymous Purchasing. This module includes software that provides the following capabilities:

[0125] allows Vendor to communicate with CVS to validate its Customers' User Session Tokens

[0126] allows Vendor to post charges onto the Customer's Clickshare Account, including posting charges to be paid to other entities such as Carriers and Affiliates

[0127] allows Vendor to obtain a list of customer-defined address identifiers so that it can ask the customer which address it should use, without obtaining any details of the addresses

[0128] allows Vendor to communicate with Carriers to obtain shipping id and pricing information

[0129] allows Vendor to communicate with the Clickshare-CAP Settlement Service to retrieve confirming information on transactions logged by the Vendor

[0130] This module can be implemented as a collection of web server components and stand-alone programs.

[0131] Destination Address Resolution Module (DARM) [Carrier]

[0132] The Destination Address Resolution Module allows Carriers to connect to the Clickshare-CAP Network to retrieve Customer address information and to respond to requests from Vendors and Customers. This module includes software that provides the following capabilities:

[0133] allows Carrier to communicate with CVS to validate Customers' Tokens, receive from CVS a Token giving them the capability to retrieve the Customer's address information from their Billing Agent, and to communicate this request to the Billing Agent

[0134] allows Carrier to communicate with CVS to facilitate securely sending a code back to the Vendor to be placed on the physical goods to be shipped

[0135] allows Carrier to respond to Vendor requests for shipping

[0136] This module can be implemented as a collection of web server components and stand-alone programs.

[0137] Site-specific Customer Identifier Module (SCIM) [part of UAM]

[0138] The Site-specific Customer Identifier Module allows a Billing Agent to generate and send an identifier that uniquely identifies the user on a particular site, but that differs for each site so that multiple sites cannot combine information about the User. Like all personal information, the User must explicitly authorize the release of a Site-specific Customer Identifier (SCID) to a particular site. Releasing a SCID to a site will allow that site to recognize when the same user contacts the site in the future. This lets the site maintain its own User-specific information. Releasing a SCID to a Vendor will allow the Vendor to build up a database of the Customer's activity on the Vendor's site, still without knowing who the Customer is. Releasing a SCID to a Shipper lets the shipper maintain special shipping instructions for the user.

[0139] Users do not need to know or remember SCIDs. They are managed entirely by their Billing Agent and the site to which the SCID was given.

[0140] Affiliation Certification Module [affiliates]

[0141] The Affiliation Certification Module allows a website to certify to others that a specific User is a member of a particular group, without releasing any identifying information about the User. Vendors can send a Customer's Session Token to an Affiliate site to ask if the User that the Token represents is a member of the Affiliate's group. The Affiliate site uses this module to communicate with CVS and the Customer's Billing Agent to retrieve the Customer's SCID and from this can determine if that Customer has previously been determined to be a member of the Affiliate's group. If the Customer has never registered with the Affiliate site, the Affiliate site can ask the Customer for information specific to the group that will identify the Customer as a member of the group. For example, the Automobile Association of America (AAA) might set up an Affiliate website that certifies whether a Customer is a member of AAA and, thus, eligible for discounts at various Vendor sites. When a Vendor site asks the AAA site to certify a Customer that has never been certified previously, the AAA site asks the Customer for a SCID, an AAA member number and additional information given when the Customer joined AAA. If the information matches the AAA member database, the AAA site remembers that the SCID corresponds to a valid AAA member and returns an affirmative response. Later, if another Vendor asks to certify the Customer, the AAA site retrieves the Customer's SCID, determines that the AAA membership is still valid and then sends an affirmative response.

[0142] In addition to certifying membership, an Affiliate site can be configured to either charge or pay the requesting site a fee for every affirmative certification that results in a sale, with the payment handling provided by the Clickshare-CAP Settlement Service.

[0143] CAP Settlement Service (CSS) [backend payment distribution]

[0144] The CAP Settlement Service (CSS) handles all of the logging and payment distribution among the players in CAP transactions. The CSS logs all CVS transactions and distributes these transaction logs to the various players: Vendors, Billing Agents, Carriers, and Affiliates, with each receiving only the logs pertaining to their function. In addition, the CSS aggregates the credits and debits for each site and handles, via the ACH or other financial network, the moving of money from site to site.

[0145] Information Flow Processes

[0146] In this section we describe the flow of information among the Clickshare-CAP components in a variety of situations.

[0147] Starting a Clickshare-CAP Session

[0148] Whenever a Customer attempts to access a Vendor's Clickshare-protected URL, the Vendor's CVM software looks for a User Session Token that it can send to the CVS for validation. There are two ways for Customers to obtain a User Session Token from their Billing Agent. If the Vendor's CVM software cannot find the Token, the Vendor asks the Customer to identify their Billing Agent and temporarily directs the Customer's browser to the Billing Agent's Login URL. Alternatively, Users can explicitly (or implicitly) begin a Clickshare-CAP Session by going to their Billing Agent's Login URL prior to requesting a Vendor's URL. We summarize the preferred implementation of these two processes below:

[0149] Scenario-A: Starting a Clickshare-CAP Session Directly from Vendor

[0150] Referring to FIG. 2, Starting a Session at a Vendor:

[0151] 1. Customer contacts Vendor and eventually requests a Clickshare-Protected URL. [Step 1]

[0152] 2. Vendor's CVM software looks for a User Session Token, and when not found, asks the Customer to provide their Billing Agent site name.

[0153] 3. Vendor redirects Customer's browser to the Login URL on the indicated Billing Agent along with instructions on where to return that user after the session has been created. [Step 2]

[0154] 4. Billing Agent asks for identifying information. This is usually a user name and password, but in some contexts may be intuited from the connection itself (e.g., ISP/Telco Billing Agents may be able to identify the User from the cell phone browser, or DSL connection).

[0155] 5. If the Billing Agent accepts the User's information, it asks CVS to begin a new session. CVS responds with a new User Session Token. [Steps 3 & 4]

[0156] 6. The Billing Agent directs the User's browser back to the Vendor's site, passing along the new Token. [Step 5]

[0157] Scenario-B: Starting a Clickshare-CAP Session on Billing Agent

[0158] Referring to FIG. 3, Starting a Session at User's Agent:

[0159] 1. User contacts their Billing Agent's Login Page. [Step 1]

[0160] 2. Billing Agent asks its User for identifying information.

[0161] 3. If the Billing Agent accepts the User's information, it asks CVS to begin a new session. CVS responds with a new User Session Token. [Steps 2 & 3]

[0162] 4. Billing Agent returns to the User's browser a customized page of links to content on the Billing Agent's site or other Vendors' sites. [Step 4]

[0163] Sending Digital BoxCar(TM)s

[0164] The Clickshare-CAP Network allows clients to securely exchange information. The CVS acts as a negotiator, confirming the validity of each side of the transfer to the other and confirming the integrity of the Digital BoxCar(TM) data. Clients use the following process in a preferred implementation to pass data securely:

[0165] Referring to FIG. 4: Sending Digital BoxCars:

[0166] 1. Sender creates a Digital BoxCar(TM).

[0167] 2. Sender asks CVS to generate a Client Token whose hash includes the Digital BoxCar(TM). [Steps 1 & 2]

[0168] 3. Sender sends the Token and Digital BoxCar(TM) to the Receiver. [Step 3]

[0169] 4. Receiver asks CVS to validate the Token, which implies verifying that the Digital BoxCar(TM) has not been tampered with. [Step 4]

[0170] A Receiver can respond using the same process.

[0171] Basic Anonymous purchase of digital content:

[0172] The simplest Clickshare-CAP transaction is the anonymous purchase of digital content. In these transactions, the Vendor immediately delivers the content to the Customer over the Internet.

[0173] In this and following scenarios, we assume that the Customer already started a Clickshare-CAP User Session using one of the preceding scenarios.

[0174] Referring to FIG. 5, Anonymous Digital Purchase:

[0175] 1. A Customer requests a Vendor's Clickshare-protected URL. [Step 1]

[0176] 2. The Vendor validates the token and determines access rights, and if a purchase is involved, the cost of the content to be delivered. [Steps 2 & 3]

[0177] 3. The Vendor checks various Confirmation and Credit Limit thresholds, asking the Customer to confirm the purchase price, if necessary.

[0178] 4. If access is allowed, the Vendor logs the transaction with CVS, along with purchase price, if any. [Steps 4 & 5]

[0179] 5. Vendor delivers the content to the Customer's browser. [Step 6]

[0180] Basic Anonymous purchase involving an Affiliate

[0181] A Vendor may wish to confirm that a Customer is a member of one or more groups or associations in order to determine access rights or cost. The Customer's experience is similar to the previous example with the following additions:

[0182] Referring to FIG. 6, Affinity Certification:

[0183] 1. Either before or after validating the Customer's Token, the Vendor tells the Customer the organizations with which it has special deals and asks the Customer to select the organizations of which they are members. [Step 1]

[0184] 2. The Vendor asks CVS for a Token that represents the capability to ask for affiliation confirmation. [Steps 2]

[0185] 3. For the organization with the best deal (or each selected organization, if desired) the Vendor redirects the Customer's browser to the organization's Affiliate Certification Server, sending the Customer's Token, the Vendor's Token, and instructions for returning the Customer's browser to the Vendor. [Step 3]

[0186] 4. The Affiliation Certification Server validates the Vendor's Token and uses the Customer's Token to request information about the Customer, primarily their SCID (this process is described earlier). [Steps 4-8]

[0187] 5. If the Affiliation Server has not previously seen the SCID or the Customer did not provide the necessary identifying information, the Server asks the Customer to release from their Billing Agent or otherwise provide information that identifies the Customer as a member of the organization. This information may include such items as the Customer's name and address (released from Billing Agent rather than typed in fresh), and a membership number. If the Customer previously provided sufficient information to the organization's Server, the Server will receive the latest version of the information previously released from the Billing Agent, and can use the SCID to look up any information the Customer provided directly to the Affiliation Certification Server, such as their membership number. The Server can then match this information against their membership database and determine the proper response to return to the Vendor.

[0188] 6. The Affiliation Certification Server redirects the Customer's browser back to the Vendor according to the Vendor's instructions, along with a Digital BoxCar(TM) containing the Server's response. [Step 9]

[0189] 7. The Vendor uses the CVS to authenticate the Digital BoxCar(TM) and adjusts its handling of the Customer according to the response from the Affiliation Certification Server. [Step 10]

[0190] Basic Anonymous purchase involving a Carrier (CAP)

[0191] The previous two processes cover purchases of Digital (intangible) goods. Here we describe the process, in the preferred implementation, for the anonymous purchase of Physical (tangible) goods. This process is very similar to that for confirming Affiliations.

[0192] Referring to FIG. 7, Anomymous Physical Purchase:

[0193] 1. A Customer requests a Vendor's Clickshare-protected URL representing the desire to purchase some physical goods. [Step 1]

[0194] 2. The Vendor validates the token, determines access rights, and if a purchase is involved, the cost of the content to be delivered. [Step 2]

[0195] 3. The Vendor checks various Confirmation and Credit Limit thresholds, asking the Customer to confirm the purchase price, if necessary.

[0196] 4. The Vendor asks the Customer to select a Carrier from the list of Carriers the Vendor uses.

[0197] 5. The Vendor asks CVS for a Token that represents the capability to ask a Carrier for a shipping identifier.

[0198] 6. The Vendor redirects the Customer's browser to the Carrier's server, sending the Customer's Token, the Vendor's Token, and a basic description of the packages, if available (number, weight, export restrictions). [Step 3]

[0199] 7. The Carrier Server validates the Vendor's Token and uses the Customer's Token to request information about the Customer, primarily their SCID, shipping address, and any additional shipping instructions stored on the Customer's Billing Agent (this process is described earlier). [Steps 4-8]

[0200] 8. If the Carrier Server has not previously seen the SCID, the Server asks the Customer to release from their Billing Agent or otherwise provide the necessary shipping instructions.

[0201] 9. The Carrier Server assigns a shipping identifier and preliminary shipping costs, if possible.

[0202] 10. The Carrier Server redirects the Customer's browser back to the Vendor according to the Vendor's instructions, along with a Digital BoxCar(TM) containing the Server's response. [Step 9]

[0203] 11. The Vendor uses the CVS to authenticate the Digital BoxCar(TM) and, if appropriate, adjusts the Customer's retail cost according to the response from the Carrier's Server. [Step 10]

[0204] 12. The Vendor validates the Customer's Token and logs the transaction with CVS, along with purchase price, if any, or with an identifier the Carrier will use later to fill in the shipping cost to be paid to the Carrier.

[0205] 13. The Vendor packages the physical goods, labeling the packages with the shipping identifier received from the Carrier.

[0206] 14. The Carrier picks up the packages and prints a complete label using the information it received from the Customer or their Billing Agent.

[0207] 15. If directed by the Vendor's instructions, the Carrier logs an addendum to the Vendor's transaction with the wholesale cost of the shipping to be paid directly to the Carrier rather than the Vendor.

[0208] Clickshare-CAP Inventions

[0209] Our technology infrastructure provides the means to realize a number of unique inventions related to Completely Anonymous Purchasing. In this section we describe these inventions and how we use our technology infrastructure to realize each invention.

[0210] Completely Anonymous Purchasing

[0211] Invention: Applying Internet tools to pass user data directly from Customer's Billing Agent to the Carrier.

[0212] Description:

[0213] We provide CAP via a combination of technology that has the following characteristics:

[0214] 1. A means to provide Customers the ability to select a trusted agent to handle their Clickshare Account and manage their personal information, including their name, address, and other shipping information.

[0215] 2. A means to securely post charges onto a Customer's account without compromising the User's anonymity.

[0216] 3. A means to obtain a shipping identifier from a Carrier that does not provide any personal information about the user.

[0217] 4. A means for a Carrier to easily obtain a Customer's shipping information.

[0218] Realization:

[0219] Customers select a Billing Agent to handle their Clickshare-CAP Account and manage their personal information, including their name, address, and other shipping information.

[0220] When a Customer selects goods from a Vendor that require shipping, the Customer briefly goes to the Billing Agent's website and authenticates, which begins a Clickshare-CAP User Session. The CVS generates a Token and passes that to the Billing Agent, which in turn passes it to the Vendor, using any of a number of transport mechanisms (e.g., URL appends, Cookies, Direct communication).

[0221] The Vendor site selects a Carrier and sends to the Carrier, the Token and possibly other information, such as package size, weight, and number, hazardous materials notations, special delivery options.

[0222] The Carrier validates the Token and requests a new Token giving the Carrier permission to request the User's SCID and shipping information. The Carrier then sends this request to the Customer's Billing Agent, which is identified in the Customer's Token.

[0223] The Customer's Billing Agent determines if the user has previously given permission to release this information to this specific Carrier, and if so, sends the requested information. If not, either the Billing Agent or the Carrier asks the Customer for permission. If the Customer agrees, the information is sent. Otherwise, a failure is propagated back to the Vendor, which cancels the sale.

[0224] Once the shipping information has been sent to the Carrier, the Carrier generates a shipping identifier for the Vendor to place on the packages and pricing information to be viewed by the Vendor. The Carrier passes this information back to the Vendor using a Digital BoxCar(TM) whose contents the CVS can later validate.

[0225] The Vendor completes the purchase by validating the Customer's Token and logs the purchase including both the charges to the Customer's account and a split of funds to be delivered to the Carrier and any Affiliates that may be involved.

[0226] Once the purchase has been completed, the Vendor packages the goods and marks them with the shipping identifier and transfers the package to the Carrier.

[0227] The Carrier brings the package to its local distribution center where the shipping identifier is replaced by a complete label with the Customer's address.

[0228] Finally the package is delivered using the existing transport infrastructure.

[0229] Additional Unique Attributes:

[0230] All Customer's personal information is managed from a single location. Carriers always get latest information.

[0231] Vendors can use many different shippers. Customer's can easily release shipping information to any Carrier, and can choose not to as well.

[0232] Carrier can easily “sign up” Vendors without any added effort. All Vendors have the same procedures.

[0233] Shipping procedures are simpler, require less information management, and are less error prone-no copying of addresses, no mistyped or out-of-date addresses or credit card numbers.

[0234] Requires nearly no changes to current Carrier business practices-just set up the Carrier web server and modify existing label preparation to generate labels from shipping identifiers.

[0235] Supports both wired and wireless web-based Internet interfaces for Customers and can be easily integrated with private network solutions such as e-book reader hardware, Palm devices, etc.

[0236] Shipping without an Address

[0237] Invention: Simplified “address-less” Vendor shipping process

[0238] Description:

[0239] Address-less shipping is beneficial even aside from the Anonymous Purchasing benefits. The Vendor can ship physical goods without the expense of managing physical addresses. The Vendor electronically receives a single shipping identifier, which is all that it needs to place on the shipping label. The Carrier does the rest. This avoids many problem areas for the Vendor:

[0240] mis-typed addresses in Customer forms

[0241] addresses lost or mangled when transferring to labels or other systems

[0242] out-of-date addresses stored from previous purchases

[0243] Customer push-back due to annoyance at having to provide shipping information

[0244] Customer push-back due to reluctance to provide personal information.

[0245] Realization:

[0246] Same as for the Completely Anonymous Purchasing invention, but without some of the additional constraints on anonymity. For example, the Vendor can still ask user for other personal information that may improve the Customer's buying experience.

[0247] Additional Unique Attributes:

[0248] Same as for the Completely Anonymous Purchasing invention.

[0249] Sales without Customer Account Management

[0250] Invention: A mechanism to enable Vendors to sell physical goods remotely without a complex e-commerce Customer Account Management System.

[0251] Description:

[0252] One of the major hurdles to creating an on-line store is managing the Customer Account Relationship. Our invention leverages existing account relationships to allow new e-tailers to sell goods without having to register Customers, obtain any payment information, or set up credit card processing systems. Instead, Billing Agents where 15 Customers are already registered handle User Management. The Vendor simply installs the Customer Validation Module, which validates Customers' Tokens and logs purchases via the CVS. Then, periodically, the CSS transfers funds into the Vendors bank account corresponding to the purchases the Vendor logged.

[0253] This invention is useful independently of Completely Anonymous Purchasing. However, together they greatly simplify the Vendor's job and reduce costs.

[0254] Realization:

[0255] Same as for the Completely Anonymous Purchasing invention, but optionally without the diversion to the Carrier to handle address-less shipping.

[0256] Additional Unique Attributes:

[0257] No longer limited to a few payment vehicles—Customers pay with any means supported by their chosen Billing Agent

[0258] Vendor can accept Customers from any Billing Agent-no 1-to-1 deals are necessary

[0259] Direct Payments to Carriers

[0260] Invention: A mechanism to simplify shipping procedures by paying the Carrier directly from funds collected from Customers by a third-party processor.

[0261] Description:

[0262] One of the extra tasks Vendors must handle is paying Carriers. This task can be taken over by the Clickshare-CAP Network, since all of the infrastructure and information already exists. The Vendor simply instructs the Clickshare-CAP Network, when it logs a purchase, to assign part of the purchase price for the transaction to the Carrier.

[0263] Realization:

[0264] Same as for the Address-less Shipping invention, but with the Carrier payment data added to the purchase transaction log.

[0265] Customer-Carrier Deals

[0266] Invention: A mechanism to allows Carriers to arrange special deals with individual Customers or Customers associated with some group, independent of the Vendor.

[0267] Description:

[0268] A Carrier can offer Customers special savings to encourage the Customers to choose that Carrier. These deals can be independent of Vendor so Carriers can market directly to Customers. Since the Carrier computes the price when assigning a shipping identifier, the Carrier is free to take into account Customer information (e.g., 10% discount if you click on this ad; or if you send us your email; or if you select us for 5 packages this month).

[0269] Realization:

[0270] Same as for the Address-less Shipping invention, but with the Carrier adjusting fee computation according to information it has about the Customer, or affiliation information it obtains from an Affiliation Server.

[0271] Additional Unique Attributes:

[0272] Builds Customer loyalty across all Vendors

[0273] Requires no additional infrastructure or process

[0274] Anonymous Package Tracking

[0275] Invention: A mechanism that allows Vendors to receive delivery status information without revealing location or other Customer information.

[0276] Description:

[0277] Vendors must be able to determine when and if the packages they sent have been delivered. The shipping identifier amounts to a special tracking number that can be used to securely retrieve tracking information from the Carrier's web site and DARM software. The tracking number can be packaged in a Digital BoxCar(TM) along with the Vendor's Token and sent to the Carriers DARM software. Upon receipt, the Carrier's software validates the token and Digital BoxCar(TM). If these are valid, it looks up the package's status through custom software and returns the result, careful to omit any reference to specific locations, delivery address, or Customer identifying information.

[0278] Realization:

[0279] The Digital BoxCar(TM) and Vendor Token capabilities are part of the technology infrastructure used to realize the Completely Anonymous Purchasing invention. The DARM software provides an additional interface to process Vendor queries.

[0280] Additional Unique Attributes:

[0281] Access to package status is secured from view by anyone other than the Vendor.

[0282] Package Tracking by Customer without Tracking Numbers

[0283] Invention: A mechanism to allow Customers to track packages being sent to them without needing to get any information from the sender, not even a tracking number or Carrier name.

[0284] Description:

[0285] Customers frequently want to know where their package is. With this invention, Customers can locate their packages without having to contact the Vendor for tracking number information. As soon as the purchase has been logged, the Clickshare-CAP system has sufficient information for the Customer to contact the Carrier directly and inquire about the shipment. This is done securely, so only the Customer can access this information via the web.

[0286] Realization:

[0287] In the course of Completely Anonymous Purchasing or Address-less Shipping, the Vendor completes a purchase by logging a transaction with the Clickshare-CAP Network. Although the Customer cannot access this information directly, the Customer can access their transaction log via their Billing Agent (and the UAM software). The transaction information includes the Carrier's Clickshare-CAP Identifier and the shipping number the Carrier returned to the Vendor. This information can be used to contact the Carrier with a User Session Token and a Digital BoxCar(TM) containing the shipping information.

[0288] When a Carrier website receives a tracking request, it validates the User Session Token and requests the Customer's SCID. If the Token was valid, the SCID will match to the SCID used when the shipping identifier was created.

[0289] The shipping identifier is then used to look up the package tracking number or indicate that the package has not yet been picked up and assigned a tracking number. The tracking number can then be used to locate the package, with the results sent back to the Customer's browser.

[0290] Additional Unique Attributes:

[0291] Builds customer loyalty to Carrier due to ease of use.

[0292] Ensures that only the Customer that made the purchase can retrieve the tracking information.

[0293] Real-Time Information Tracking

[0294] Invention: A mechanism that allows Customers to view their transaction logs in real-time.

[0295] Description:

[0296] The Clickshare-CAP Network maintains a log of all of the requests made to the CVS. Although Users cannot access this log directly, they can review a log of their own transactions via their Billing Agent. Depending on their Billing Agent's configuration, Users can either review past transactions, review recent transactions by explicitly requesting updates, or review transactions in real-time. In any form, providing this review improves security since the User can always determine exactly what information was released to whom and what purchases have been logged. The real-time mode can be supported if the Billing Agent is willing to retrieve transactions from the CSS frequently and update the User's display:

[0297] Realization:

[0298] Every significant action the CVS takes generates a log entry in the CSS database. Billing Agents poll this database periodically looking for transactions logged on behalf of the Billing Agent's Users.

[0299] The UAM software can respond to User requests to view the transaction log by either querying the CSS once, every time the user asks for an update, or more frequently. Each time new transactions arrive the UAM can format the results and display them to the User.

[0300] Additional Unique Attributes:

[0301] Only a Billing Agent and its users (and the CSS) can view the transaction logs for a particular User.

[0302] Provides a trusted log of information released to all parties.

[0303] Allows Users to quickly spot system failures or improperly operating Clickshare-CAP clients.

[0304] Customized Delivery Instructions

[0305] Invention: A mechanism to allow Customers to add special delivery instructions reliably.

[0306] Description:

[0307] When Customers remotely purchase goods for delivery they currently depend on the Vendor to pass on any special delivery instructions. Instructions such as “Leave package next door if no one is home” are easily missed when the Vendor arranges to ship the goods. Customers using the Clickshare-CAP Network, however, avoid this problem since they can communicate directly with the Carrier.

[0308] Realization:

[0309] When a Customer first releases their address information to a specific Carrier, the Customer can provide special instructions. Customers can also place special instructions in the shipping information stored at their Billing Agent, so whenever they release this information to any Carrier, the Carrier sees any special instructions. Storing the information on the Billing Agent has the added benefit that the Customer can update the special instructions once and all future shipments will use the updated instructions.

[0310] Additional Unique Attributes:

[0311] Avoids shipping delays and mis-communication

[0312] Allows the Carriers to better serve their Customers

[0313] Certified Affiliations

[0314] Invention: A mechanism to determine if a Customer is a member of a special group reliably and anonymously.

[0315] Description:

[0316] Frequently, Vendors have special arrangement with Customers that belong to particular groups or organizations. For example, members of the American Automobile Association (AAA) may get discounts when purchasing travel books. Vendors can use the authentication capabilities of the Clickshare-CAP Network to validate Customers' affiliations.

[0317] Realization:

[0318] When a Customer arrives on a Vendor's site the Vendor can ask if the Customer is a member of any groups with which the Vendor has a special arrangement. For example, a book vendor might ask if the Customer is a member of AAA, AARP, or IEEE.

[0319] If the Customer selects AAA, the Vendor sends the Customer's Token to AAA's Affiliate Server.

[0320] The AAA server validates the Token, asks for the User's SCID.

[0321] If the server has previously determined that the Customer with that SCID is a member in good standing, the server sends an affirmative response back to the Vendor in a Digital BoxCar(TM).

[0322] If the server has never seen the SCID before, the server can ask the Customer for identifying information such as an address and member ID to determine membership.

[0323] When the Vendor receives the response, it can validate the Digital BoxCar(TM) and act accordingly.

[0324] Additional Unique Attributes:

[0325] User only needs to enter membership information once.

[0326] Affiliate Server can dynamically check that membership is in good standing and can offer Customer special deals, such as membership extensions and level increases.

[0327] Vendor knows if the Customer is a member of the group, but not any other identifying information.

[0328] Affiliate Server can accurately track Customer's use of special offers and discounts.

[0329] Affiliate Server and Vendor can arrange for one or the other to be paid a commission for every certification that results in a purchase in a similar manner as described in the section on the Direct Payments to Carriers invention.

[0330] A similar mechanism could be use to certify that the Customer's address is not within an export-controlled area: Vendor sends export restriction category to Carrier, which checks if the address is OK.

[0331] Summary: Completely Anonymous Purchasing

[0332] The Clickshare-CAP Network provides a unique technology infrastructure that supports a collection of inventions supporting Completely Anonymous Purchasing. The principal ideas are:

[0333] 1. Customers select a Billing Agent, separate from the Vendor, to handle the Customer's account and to store and manage the Customer's personal information. This, along with the Network's authentication capabilities, allows Vendors to charge Customers for their purchases without the Customer providing any identifying information.

[0334] 2. Customers release their name, address, and other shipping information to Carriers directly, bypassing the Vendor site.

[0335] 3. The Carriers supply a shipping identification that allows Vendors to present the packages to the Carrier without having to know any identifying information about the Customer.

[0336] The Clickshare-CAP Network also supports other unique capabilities such as Affiliation Certification, special deals between Carriers and Customers, simplified package tracking for Customers, and others.

[0337] It is obvious that minor changes may be made in the form and construction of the invention without departing from the material spirit thereof. It is not, however, desired to confine the invention to the exact form herein shown and described, but it is desired to include all such as properly come within the scope claimed. 

1. A system for anonymous purchase of goods involving a Carrier who delivers the goods to the Customer, comprising the steps of: a. a Customer requests a Vendor's Clickshare-protected URL representing the desire to purchase some physical goods, b. the Vendor validates the token, determines access rights, and if a purchase is involved, the cost of the content to be delivered, c. the Vendor checks various Confirmation and Credit Limit thresholds, asking the Customer to confirm the purchase price, if necessary, d. the Vendor asks the Customer to select a Carrier from the list of Carriers the Vendor uses, e. the Vendor asks CVS for a Token that represents the capability to ask a Carrier for a shipping identifier, f. the Vendor redirects the Customer's browser to the Carrier's server, sending the Customer's Token, the Vendor's Token, and a basic description of the packages, if available (number, weight, export restrictions), g. the Carrier Server validates the Vendor's Token and uses the Customer's Token to request information about the Customer, primarily their Site-specific Customer Identifier (SCID), shipping address, and any additional shipping instructions stored on the Customer's Billing Agent (this process is described earlier), h. if the Carrier Server has not previously seen the SCID, the Server asks the Customer to release from their Billing Agent or otherwise provide the necessary shipping instructions, i. the Carrier Server assigns a shipping identifier and preliminary shipping costs, if possible, j. the Carrier Server redirects the Customer's browser back to the Vendor according to the Vendor's instructions, along with a Digital BoxCar(TM) containing the Server's response, k. the Vendor uses the CVS to authenticate the Digital BoxCar(TM) and, if appropriate, adjusts the Customer's retail cost according to the response from the Carrier's Server, l. the Vendor validates the Customer's Token and logs the transaction with CVS, along with purchase price, if any, or with an identifier the Carrier will use later to fill in the shipping cost to be paid to the Carrier, m. the Vendor packages the physical goods, labeling the packages with the shipping identifier received from the Carrier, n. the Carrier picks up the packages and prints a complete label using the information it received from the Customer or their Billing Agent, o. if directed by the Vendor's instructions, the Carrier logs an addendum to the Vendor's transaction with the wholesale cost of the shipping to be paid directly to the Carrier rather than the Vendor, and p. the Carrier delivers the goods to the Customer. 